Add resource to manage ML anomaly detection jobs #1329
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
nick-benoit
reviewed
Oct 20, 2025
tobio
added a commit
that referenced
this pull request
Oct 23, 2025
* origin/main: Add resource to manage ML anomaly detection jobs (#1329) chore(deps): pin alpine/mkcert docker tag to a8f4f5a (#1389) Bump version in Makefile (#1388) Update changelog for 0.11.19 and 0.12.1 (#1387) Security Detection Rule schema validation improvements (#1381) Remove connector client generation make task (#1386) Fixup changelog link Move local environment to docker compose managed services (#1384) chore(deps): update golang:1.25.3 docker digest to 8c945d3 (#1385)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #520
This resource only manages the existence of an anomaly detection job, it does not manage the state (open/closed). I'm planning on adding another resource to purely manage that state, it's an independent API. IMO it's simpler for practitioners if these are separate resources altogether.